

                                           OutlookToSIN Integration Software Acceptance Test Plan (V0.6)
                                           =============================================================
                                           =============================================================

1. Targeted Outlook Applications
   =============================

       1.1 Targeted Outlook Applications include: Outlook2003, Outlook2002, Outlook2k and Outlook98.

       1.2 Targeted Outlook Modes: 
                        1.2.1 Internet Mail.
                        1.2.2 Corporate or Workgroup (C/W) mode.

       1.3 Targeted Mail Accounts:
                        1.3.1 PST file and POP3/SMTP transport provider.
                        1.3.2 Exchange account.

2. Targeted Client Platforms
   =========================

       2.1 Targeted Platforms include: WinXP Pro, WinXPHome, Win2k, WinNT, and Win98.

   	

3. Outlook-Addin Software Installer
   ================================

       3.1 The installer software is expected to automatically install and configure the 
           OutlookToSIN extended features including any 3rd party software on a customer pc/laptop.
           The installer software must include the installer and the uninstaller utilities. 

       3.2 The installer/addin software must provide a gui utility to configure the main parameters
           including:
           2.2.1 SIN Server IP Address and Port Number.
           2.2.2 The option of using an Http Proxy and bypassing selected IP addresses. 
                 The possibility of using the Internet Explorer settings to configure the 
                 proxy should be supported.
           2.2.3 The user login info and password.
           2.2.4 Notification Recipient. 
           2.2.5 The ability to apply/cancel the entered data.
       
       3.3 The installer must detect correctly whether there is an Outlook application 
           running or not and displays the needed message asking the user to close and restart,
           after completing the installation, his/her Outlook if it is already running.

       3.4 The installer must display the deployment agreement and force the user to accept/reject
           the agreement terms.

       3.5 The installer must give the user the ability to select the installation target directory
           and create it if it is not already created.
            
       3.6 The uninstaller (removal) utility must correctly detect whether an Outlook application 
           is currently running and instructs the user to close his outlook in order to 
           complete the uninstall procedure. 

       3.7 The uninstaller must physically and logically remove all the related files and 
           folders and any reserved memory cache if applicable.

       3.8 The installer gui must display the correct logo in accordance with the 
           Pinpoint Selling trademarks.
               


4. Graphical User Interfaces (GUIs) Look & Feel Requirements
   =========================================================

       4.1 Pinpoint Options
           The Pinpoint Options window must be opened via a tool bar button, the "Pinpoint Options" button
           on the main Outlook application gui. 
           This window must provide the following post-installation configuration abilities: 
          
           4.1.1 SIN Server IP Address and Port Number.
           4.1.2 The option of using an Http Proxy and bypassing selected IP addresses. 
                 The possibility of using the Internet Explorer settings to configure the 
                 proxy should be supported.
           4.1.3 The user login info and password.
           4.1.4 Notification Recipient.
           4.1.5 The ability to apply/cancel the entered data.                                                               
                     
       4.2 The Extended Message Form
           The extended message form must be opened via a tool bar button, the "New Pinpoint Mail"
           on the main Outlook application gui.
           This form should be augmented with all the required widgets/fields including:
           4.2.1 SIN login button - "Send Sales Package".
           4.2.2 Domain Selection Drop Down List.
           4.2.3 Package Selection Drop Down List.
           4.2.4 Package Customization Button - "Customize Package".
           4.2.5 Package Previewing Button - "Preview Package".
           4.2.6 BCC Field.
           4.2.7 Message Body: 
                 a. "Salutation/Name" Tag.
                 b. "Type Here..." Text field.
                 c. "Please Click Here" Tag.
          


5. Functional Requirements
   =======================

   5.1 The Extended Message Form
       -------------------------

       5.1.1 With the add-in installed, each time a new message (new Pinpoint Mail) form is opened (From Outlook) 
             and the MSWord editor is being used, an info message should be displayed informing
             the user not to use MSWord if he/she wants to use the SIN integration feature.
             A detailed use case scenario is presented below:
             1. The Outlook to SIN add-in is installed.
             2. During installation, a message is displayed informing the user not to use MS Word if he/she wishes to 
                use the PPS integration feature.
             3. The user wishes after a while to use the MSWord editor and enjoy the features of MS Word in his regular mail.
                To do so, the user performs the following:
                3.1 Tools --> Options --> Mail Format --> Message Format --> select MS Word
                    When the user chooses this option then all new message forms will be MS Word Edited automatically.
 
                3.2 Actions --> New Mail Message Using --> MS Word
                    In this option, Outlook displays a message asking the user whether he/she wants to use MS Word 
                    in all subsequent messages or only in the current one. The user makes the choice.
  
             In either case above 3.1 or 3.2 [only if the user chooses to use MSWord in all subsequent messages], 
             when a "New Pinpoint Mail" button is clicked, one of the following two behavior is required:
             
             A. The extended message form is opened and is set to always use the Outlook HTML editor regardless 
                of what the user has selected as the editor for his/her regular mail. This is the preferred behavior.
             B. The PPS add-in must detect that MS Word is being used.
                At this instance, a message window is required to inform the user not to use MS Word if he/she intends to 
                to use the PPS integration feature. The extended message form is never opened until the editor is set
                to the Outlook HTML editor and clicks on the "New Pinpoint Mail" button again.
             

       5.1.2 This section describes briefly the effect of logging-in to the SIN server on
             the extended message form. This will give the user/tester a quick summary of
             what to expect firstly after logging in. Further functional details are provided in the 
             following sections:

                                                      Not Logged In to SIN			          logged In to SIN
                                                      --------------------                                ----------------

             Send Sales Package (SIN login button) --  visible and enabled         ------       visible and disabled          
             
             Domain Selection Drop Down List       --  visible and disabled        ------       visible and disabled for a single-domain user
                                                                                                visible and enabled for a multi-domain user
	     
             Package Selection Drop Down List      --  visible and disabled        ------       visible and disabled for a multi-domain user
                                                                                                visible and enabled for a single-domain user

             Package Customization Button          --  visible and disabled        ------       visible and disabled for a multi-domain user
                                                                                                visible and enabled for a single-domain user
             
             Package Previewing Button             --  visible and disabled        ------       visible and disabled

             BCC Field                             --  as set by the user defaults ------       visible and populated with the email of the 
                                                                                                Notification recipient defined in the 
                                                                                                Pinpoint Selling Options window.

             The message Body                      --  empty                       ------       Body is automatically augmented with
                                                                                                - Salutation/Name Tag
                                                                                                - Type here.. Text
                                                                                                - Please Click Here Tag
                                                                              

            
       5.1.3 Domain Selection Drop Down List:
             
             This widget displays all the domains defined for the current user.
             
             A multi-domain user: 
             --------------------
             The domain selection dropdown list should be 
             enabled after a successful SIN login. No automatic selection
             is done until the user explicitly makes a selection.
                 
             A single-domain user: 
             ---------------------
             The domain selection dropdown list remains 
             disabled with the domain selection set in the background to the
             default domain being the only one. 
                     
		       
        5.1.4 Package Selection Drop Down List:
            
              This widget displays all the packages defined for the selected domain.
              
              A multi-domain user: 
              --------------------
              The dependency of enabling/disabling of the package selection dropdown list is 
              based on the selection of a domain. Once a domain is selected the list must be 
              automatically enabled.
                        
              A single domain user:
              ---------------------
              The package selection dropdown list is automatically enabled after a successful
              SIN login since the domain is already selected.
                       

        5.1.5 The "Customize Package" button should be enabled in two cases:
              A multi-domain user: 
              --------------------
              When a domain is selected from the domain dropdown list
              the "Customize Package" button should be enabled. If no domain is selected
              (same case when a domain is unselected) then the Customize Package should
              be disabled as well.                                       
                        
              A single-domain user:
              ---------------------
              The Customize Package Should be automatically enabled (with the package 
              selection dropdown list) after a successful login. 
                       
                  
        5.1.6 The "BCC" field:
              Before logging in to the SIN server, this field properties are set as desired by the user.
              After a successful SIN login, the required behavior is to display
              (made visible on the message form) the "BCC" field and automatically 
              set it to the current outlook user or another user (as set in the "Pinpoint Selling Option" 
              window under "Notifications").
              This email address will dictate where the master email (defined in an upcoming section) is sent.

                        
        5.1.7 The "Salutation/Name" Tag:                     
               - The Salutation/Name Tag (place holder) must be displayed in the message body 
                  only after a successful SIN login. 
               - This tag should be replaced by the respective customized salutation as defined by the user for
                 each invitation recipient.
               - This tag should be a floating tag which allows the user to enter text around it.
               - This tag should be read/write enabled, which means that the sender can either keep
                 this tag and use it as discussed, or delete this tag completely in the case where no 
                 salutations at all are to be sent to any of the recipients.    
           

        5.1.8 The "Type Here..." field:                     
              - The "Type Here..." text field must be displayed in the message body 
                only after a successful SIN login. 
              - This field should be editable and represents the message body.
                Hence, it can be modified by the user to enter the invitation text.  
                   
        
        5.1.9 The "Please Click Here" Tag:                     
              - The Please Click Here Tag (place holder) must be displayed in the message body 
                only after a successful SIN login. 
              - This tag should be replaced by the respective customized package link provided by the SIN server for
                each invitation recipient.
              - This tag should be a floating tag which allows the user to enter text around it.
              - This tag should be read-only.


   5.2 Sending a Sales Package (a.k.a. an invitation)
       ----------------------------------------------
       
        5.2.1 Logging-In to SIN Server
              The outlook user must perform a new SIN login request each time he/she
              wishes to send a sales package invitation. This is performed when a new message 
              form is opened and the "Send Sales Package" button is clicked. 
              The successful login task should return the respective cookie with its value
              set to the current Http Session id.                                     

        5.2.2 Http Session Tracking & Management
              Session Management is achieved by the use of Cookies and URL encoding. 
              The cookies are stored on the client side (i.e. where the Outlook application is running).
              The URL encoding is to be used in cases where no cookies are added to the Http requests.
              When the Outlook User connects to the SIN server a new Http Session is started.
              
              Session is gracefully terminated in one of the following cases:
              ---------------------------------------------------------------
                1. When UserA abandons his/her invitation:
                   This represents a case where a logged-in user decides not to proceed 
                   with the invitation, so he/she closes the message form (e.g. by using
                   the [X] button on the top right corner or the File drop down menu).

                2. After successfully notifying the server about the invitation (i.e. during the 
                   personalized links retrieval request, described below, and receiving an OK response).

                   In both cases, the Outlook application automatically perform the following actions in order:

                   Action-1. An HTTP request needs to be sent to the outlook jsp to clean up 
                             some of the SIN internal components: 
                             "http://SIN server URL/outlook/outlook.jsp?" + cookie + "&command=cancel" 

                   Action-2. An HTTP request (with the cookie), "sessionTerminationRequest", must be sent 
                             to the server to ensure that UserA has logged out from the current 
                             WebLogicSession and provide a better utilization of server 
                             resources.                       

                   Action-3. The locally stored cookie must be destroyed after receiving an OK 
                             session termination response from the SIN server.
                   
                   Note: Please note that the cookie inclusion in Action-1 & Action-2 might be redundant if it is already 
                         included by default as in the Microsoft model. 



              Session is terminated abnormally in the following cases:
              --------------------------------------------------------
                1. The SIN Server crashes or is restarted.
                
                2. The Outlook cookie is set to have a 60-minute idle lifetime. This means that the 
                   cookie will be invalid if the period of time between two successive calls exceeds
                   60 minutes.                   

                3. The server logs out the outlook user (e.g. by server admin).                           

                The Outlook application should receive an Http Status code of "408" and behave
                accordingly. Detailed handling requirements are provided in the following sections. 
        

        5.2.3 Preview Package

	      The Outlook user must have the ability to select one of the packages (standard or
              custom package) from the package selection dropdown and view it in an Internet Browser
              by clicking on the Preview Package button.
              If the user loses his/her Http Session (for the reasons discussed above) then:
              Case-1 If the user has selected a standard package, then the Outlook add-in application must:
                     - Automatically re-login to the SIN server.
                     - Stores the new cookie and discards the old one.
                     - All the other parameters should be retained including: the recipient list, 
                        selected domain, message body, invitation title. 
                     - Proceed with the preview operation automatically.

              Case-2 If the user has created and selected a custom package, then the Outlook 
                     add-in application must:
                     - Automatically re-login to the SIN Server.
                     - Stores the new cookie and discards the old one.
                     - Clears the Custom Package Entry in the Package Selection list (since there
                       is no way to access the custom package created in the previous session).
                     - Displays a message asking the user to recreate the custom package. 
                     - All the other parameters should be retained including: the recipient list, 
                       selected domain, message body, invitation title. 
                     - User must recreate the required Custom Package.
                     - Proceed with the preview operation by clicking again on the Preview Package 
                       button.              
              
	
        5.2.4  Customize Package

               The Outlook user must have the ability to create/modify/preview a customized sales package.
               The requirements stipulate that there should be a maximum of one custom package
               per domain per session.


               Case-1: A single-domain user:
                       ---------------------
                       A logged-in user must have the ability to create a max of one custom 
                       sales package per session.
                       Since the single-domain user has his/her domain automatically selected,
                       the user needs to only click on the "Customize Package" button to start the process.
                       
                       Requirements:
                       -------------
                       a. In the following requirement scenario, it is assumed that the user has only one domain: domainA.                       
                          When the user click the Customize Package button, Outlook sends two http requests 
                          to the Outlook jsp as listed below:
                          a.1:  This request will init the jsp in SIN
                                "http://serverUrl/outlook/outlook.jsp?" + cookie + "&domainId=domainAId"
                          a.2:  This request should be made to open an IE explorer on the Outlook user machine with 
                                the following request:
                                "http://serverUrl/outlook/outlook.jsp?" + cookie + "&command=jump&page=content"
	                        The user is expected to interact with the opened jsp (un)selecting/uploading the desired
                                content. When done, the user is required to click on the "Return" button on the jsp
                                to save the selection(s) and close the browser.
                          a.3:  Any encountered errors in this stage is reported directly (i.e. visually) by the 
                                jsp itself.  
                          Note: If the Outlook add-in application is using the Microsoft way of sending an Http Request,
                                then the cookie is expected to be included automatically and no need to encode it
                                in the URL as in the above approach.                    

                       b - The user must have the ability to modify an already created custom
                           package while in the same domain.
                       c - The user must have the ability to preview an already created custom
                           package while in the same domain.
                       d - If after creating a custom package the user loses his/her session 
                           (for one of the reasons discussed above). If the user wishes
                           to modify/preview/send the custom package then the required add-in behavior is as follows:
                           - Automatically re-login to the SIN Server.
                           - Stores the new cookie and discards the old one.
                           - Clears the Custom Package Entry in the Package Selection list (since there
                             is no way to access the custom package created in the previous session).
                           - Displays a message asking the user to recreate the custom package. 
                           - All the other parameters should be retained including: the recipient list, 
                             message body, invitation title.  
                           - User must recreate the lost Custom Package as required.                        
                       e - The user has the ability to abandon an already created custom
                           package and select one of the available standard packages and 
                           use it in the invitation.

               
               Case-2: A multi-domain user:
                       --------------------

                       A logged-in user must have the ability to create a max of one custom 
                       sales package per domain per session.
                       The user must select his/her domain first then click on the Customize Package 
                       button to start the process.

                       Requirements:
                       -------------
                       a. In the following requirement scenario, it is assumed that the user has two domains: domainA
                          and domainB and he/she selected domainA first.
                          When the user clicks the "Customize Package" button, Outlook sends two http requests 
                          to the Outlook jsp as listed below:
                          a.1:  This request will init the jsp in the SIN server:
                                "http://serverUrl/outlook/outlook.jsp?" + cookie + "&domainId=domainAId"
                          a.2:  This request should be made to open an IE explorer on the Outlook user machine with 
                                the following request:
                                "http://serverUrl/outlook/outlook.jsp?" + cookie + "&command=jump&page=content"
	                        The user is expected to interact with the opened jsp (un)selecting/uploading the desired
                                content. When done, the user is required to click on the "Return" button on the jsp
                                to save the selection(s) and close the browser.
                          a.3:  Any encountered errors in this stage is reported directly (i.e. visually) by the 
                                jsp itself. 

                          Note: If the Outlook add-in application is using the Microsoft way of sending an Http Request,
                                then the cookie is expected to be included automatically and no need to encode it
                                in the URL as in the above approach.  
                       
                       b - CustomPackageA is correctly created under domainA. The user may decide to preview it if need be. 
                       c - User realizes that the CustomPackageA has been created in the wrong domain. 
                       d - User selects domainB and clicks on the Customize Package button.
                       e - Outlook sends two requests to the Outlook jsp as discussed earlier and listed below:
                           e.1:  This request will init the jsp in SIN
                                 "http://serverUrl/outlook/outlook.jsp?" + cookie + "&domainId=domainBId"       
                           e.2:  This request should be made to open an IE explorer on the Outlook user machine with 
                                 the following request:
                                 "http://serverUrl/outlook/outlook.jsp?" + cookie + "&command=jump&page=content"
	                         The user is expected to interact with the opened jsp (un)selecting/uploading the desired
                                 content. When done, the user is required to click on the "Return" button on the jsp
                                 to save the selection(s) and close the browser.
                           e.3:  Any encountered errors in this stage is reported directly (i.e. visually) by the 
                                 jsp itself.  
                           e.4:  The cookie must be sent as described in order to achieve the correct session management
                                 and resource management as well. 
                           
                           Note: If the Outlook add-in application is using the Microsoft way of sending an Http Request,
                                 then the cookie is expected to be included automatically and no need to encode it
                                 in the URL as in the above approach. 

                       f - CustomPackageB is correctly created under domainB. This new custom package has no
                           relation to customPackageA at all. The user may decide to preview this package.
                       g - Before sending the invitation, user returns to domainA and clicks on 
                           "Customize Package" button. 
                       h - Outlook sends two requests to the Outlook jsp as discussed earlier and listed below:
                           h.1:  This request will init the jsp in SIN
                                 "http://serverUrl/outlook/outlook.jsp?" + cookie + "&domainId=domainAId"
                           h.2:  This request should be made to open an IE explorer on the Outlook user machine with 
                                 the following request:
                                 "http://serverUrl/outlook/outlook.jsp?" + cookie + "&command=jump&page=content"
	                         The user is expected to interact with the opened jsp (un)selecting/uploading the desired
                                 content. When done, the user is required to click on the "Return" button on the jsp
                                 to save the selection(s) and close the browser.
                           h.3:  Any encountered errors in this stage is reported directly (i.e. visually) by the 
                                 jsp itself. 

                           Note: If the Outlook add-in application is using the Microsoft way of sending an Http Request,
                                 then the cookie is expected to be included automatically and no need to encode it
                                 in the URL as in the above approach. 
                           
                       i - User gets a fresh custom package in domainA. The old customPackageA is gone and there should 
                           be no more than one Custom Package entry in the package selection drop down list.
                       j - User should get a fresh customPackageB if he goes back again to domainB and decides to 
                           create a new custom package.

                       k - The user must have the ability to modify an already created custom
                           package while in the same domain.
                       l - The user must have the ability to preview an already created custom
                           package while in the same domain.
                       m - If after creating a custom package the user loses his/her session 
                           (for one of the reasons discussed in an earlier section). If the user wishes
                           to modify/preview/send the custom package then the Outlook add-in must perform the following:
                           - Automatically re-login to the SIN Server.
                           - Stores the new cookie and discards the old one.
                           - Clears the Custom Package Entry in the Package Selection list (since there
                             is no way to access the custom package created in the previous session).
                           - Displays a message asking the user to recreate the custom package. 
                           - All the other parameters should be retained including: the recipient list, 
                             selected domain, message body, invitation title.   
                           - User must recreate the lost custom package.                   
                       n - The user has the ability to abandon an already created custom
                           package and select on of the available standard packages in his/her
                           current domain or the standard/custom packages in another domain to  
                           be used in the invitation.


        5.2.5 Delivering a standard/custom package to one or more recipients:

              Once all the invitation details are entered (i.e. domain/package selection,
              list of recipients, invitation title and body) the user must click on the
              standard "Send" button to initiate the delivery process.
              
              The delivery process consists of the following three phases which must be executed automatically
              and in order in the background:
 
              Phase-I:     Getting the personalized links (modified in the SIN to include implicit server notification):
                           In this phase, the Outlook application obtains & stores the personalized link
                           for each invitation recipient from the SIN server.
                           This request will automatically notify the SIN server of the details of the outgoing
                           invitation so that it can monitor and watch the recipients when they view the package.

              Phase-II:    The Http Session graceful termination steps (the actions stated in 5.2.2 above).                                          

              Phase-III:   Sending the invitation:
                           In this phase, copies of the original email are created (one per recipient)
                           and sent in the background to each respective recipient.
                           Each copy will have:
                           - Its Salutation/Name tag (if present) replaced with the recipient's personalized salutation.  
                           - "Please Click Here" placeholder is updated to hold the respective personalized
                             link for the recipient (obtained in Phase-I).
                           - Each copy will have only the name of its recipient in the "To" field.
                           - The master email is created and stored on the sender side.              
                               
               
              Sender Side Requirements:
              -------------------------

               a. The master email (the one BCC'd to the sender), format as shown in the appendix, 
                  must be stored in the sender's Sent Items box. The storing of the master email must
                  only be done after successful delivering of the individual invitations.
               b. If there is some work to be done that holds the outlook application, then the work must
                  be done in the background (e.g. if it takes more than what it takes to send the same email
                  with the same number of recipients in the normal way then the invitation sending must be done
                  in the background and Outlook must be freed). 
               c. The personalized invitation emails should not be stored in any of the user Outlook folders.
               d. If any of the recipients does not have his/her personalized salutation already defined by the sender
                  then a message must be displayed asking the sender to define one.
               e. If any of the recipients does not have a contact page defined in the Contacts folder, then
                  the Outlook application must create an entry for the new contact and prompt the user
                  for the recipient first name, recipient last name and the personalized salutation. This info
                  must be stored in the newly created contact page for that recipient.
               f. If the user does not enter any personalized salutation (when prompted to do so), 
                  then the respective recipient will have no Salutation (empty) in his invitation.
               g. The user must have the ability to completely delete the Salutation/Name Tag from the extended
                  message form, thereby none of the recipients will have any salutation in his/her invitation email.
               h. The Salutation/Name Tag must be floating in the extended message form, thereby permitting the user
                  to enter text around it.
               i. The user must have the ability to modify/delete a predefined personalized salutation.
               j. The "Please Click Here" Tag must be read-only and floating to allow the sender to enter text
                  around it.               
               k. The user must be able to send a sales package invitation to any number of 
                  recipients (bounded only by the SIN server defaults).
               l. If the current Http Session is invalid when the "Send" button is clicked (for one of the reasons
                  discussed in (5.2.2) then handling it depends on the following:
                 
                  l.1 If the user has selected a standard package, then the Outlook add-in application must:
                      - Automatically re-login to the SIN server.
                      - Stores and uses the new cookie and discards the old one.
                      - May use the stored (retrieved personalized links from SIN) or requery the server again.
                      - All the other parameters should be retained including: the recipient list, 
                        selected domain, message body, invitation title. 
                      - Proceed with the Sending three phases.

                  l.2 If the user has created and selected a custom package, then the Outlook add-in application must:

                      - Automatically re-login to the SIN Server.
                      - Stores and uses the new cookie and discards the old one.
                      - Clears the Custom Package Entry in the Package Selection list (since there
                        is no way to access the custom package created in the previous session).
                      - Displays a message asking the user to recreate the custom package and to click
                        on the "Send" button again to restart the invitation delivery.
                      - All the other parameters should be retained including: the recipient list, 
                        selected domain, message body, invitation title. 
                      - Proceed with the Sending three phases. 

                m. In case of a failure in retrieving the personalized links (which includes the 
                   implicit notification to the SIN) in Phase-I of the Send process
                   a message must be displayed with the error details send by the server.
                   The Send process is aborted but the invitation message form must be stored in the
                   sender's Drafts folder for future reference by the sender.      

                n. In case of a failure in any of the graceful session termination phases described in Phase-II
                   of the Send process a message must be displayed with the error details encountered by
                   the outlook application.
                   The Send process is aborted but the invitation message form must be stored in the
                   sender's Drafts folder for future reference by the sender. 

                o. In case of a failure in sending out some/all of the individual invitations in Phase-III
                   of the Send process a message must be displayed with the error details encountered by
                   the outlook application listing all the recipients that faced failures in having
                   their invitations delivered.
                  
                p. The amount of time spent by outlook in sending an invitation to:
                   - One Hundred new recipients should not exceed (X) seconds.
                   - One Hundred existing recipients should not exceed (Y) seconds.

                   Note: New/Existing recipients with respect to the SIN Database.

                   Pinpoint Selling is currently performing the required bench marking and will provide
                   the numbers once they are available.
                                
                           
              Recipient(s) Side Requirements:
              -------------------------------
              a. The invitation email must be received by all recipients.
              b. Each individual invitation will carry on the recipient name in the "To:" field.
              c. For each recipient, if the user has defined a personalized salutation for
                 that recipient, then the salutation/name tag is replaced with the customized one.
              d. The message text body should be identical to the one created by the sender.
              e. The "Please Click Here" tag in converted to hyperlink pointing to the respective
                 personalized package link returned by the SIN server in the Send Phase-I discussed 
                 earlier. 
              f. The recipient must be able to successfully view the enclosed sales package by clicking 
                 on the "Please Click Here" tag.
              g. Invitation sample in provided in the Appendix.
                            

   5.3 A Note on Cookies: 
       ------------------
    
       Based on the behavior of the Weblogic Server in refreshing the cookies, the Outlook 
       application can continue to use the original cookie (returned by the SIN server in 
       the login response) for further SIN server interactions. 


   5.4 Error Messages: 
       ----------------
    
       When an error occurs, the server sends the error details in the Http Response.
       The Outlook application must display these errors to the user and not just report
       that an error has occurred.

   5.5 Security Issues and Warnings Messages: 
       --------------------------------------
    
       When executing the SIN integration scenarios, the Outlook add-in application must not display
       any security warnings and must be able to handle all security issues that might 
       arise when deployed in the customers environments/platforms.

                

6. Appendix
   ========
                  //=====================================================================
		  //	Personalized Invitations and the Respective Master Email Example
		  //=====================================================================

		  Here is a sample use case scenario of what the personalized invitations 
                  and their respective master email looks like.
                  It is assumed that the Sender intends to include personalized salutations
                  in the individual invitations.	 

		  1. The master email (the one BCCd to the sender) should have: 
	                The same TO: list as in the originally created invitation email.
	                "BCC:" should be cleared and does not have to be visible.
	                Body does not have a salutation nor a personalized link.
	                Body has the entered text body.
                       . Body must contain the "Please Click Here" as a text field with no
                         active hyperlink underneath it.

                  2. The Individual emails expected behavior is as follows:
                     2.1 The sender must not be able view any of the internally created 
                         individual invitation emails.
                     2.2 Outlook should transparently (i.e. silently) send those emails. 
                     2.3 No copies are stored of any of those individual emails.
                     2.4 The sender should not be able to view these personalized links.
                  
                  3. The expected salutation phrase solution is to have a tag (i.e. a place 
                     holder) in the original email body.
                     Upon sending the invitation, on each individual email, Outlook replaces 
                     this tag with a stored salutation/Name 
                     Details of the respective recipient as follows:
                     <Salutation/Name Tag(place holder)>  ---- to be replaced by  
                     the personalized/predefined and configurable salutation/name field.
                     For example, for contact A, the user might wish to address him/her with: "Hi A", 
                     the second one might be "Greetings", the third contact might
                     be "Dear Mr. X Y Jr." and so forth. 
                     
                     For example, let us say that we have two recipients on the original invitation email:
                     james.kirck@startrek.com and eliot.ness@untouchables.com
                     It is expected that a personalized salutation is already entered by the user and stored
                     in Outlook for each recipient.
                     At this stage, the original invitation email looks like this
  	             ----------------------------
	             To: james.kirck@startrek.com;eliot.ness@untouchables.com
	             BCC: the sender email
                     Subject: invitation subject
                     <Salutation/Name Tag(place holder)>
	               Core Text body
	             <Please Click Here> (personalized link place Holder)
 	             -----------------------------

                     The two individual emails created by Outlook and never seen by the 
                     sender look like this:

	             -----------------------------------------------

                     To: james.kirck@startrek.com
	             BCC:
                     Subject: invitation subject
                     Dear James Kirck      
	             Core Text body as entered by sender
	             Please Click Here (the underlying is Jame's personalized link)

                     --------------------------------------------------

	             To: eliot.ness@untouchables.com
	             BCC:
                     Subject: invitation subject
                     Mr. Eliot Ness Jr.    
	               Core Text body as entered by sender
	             Please Click Here (the underlying is eliot's personalized link)

	             --------------------------------------------------

	             The Master email, i.e. the one received by the Sender would look like:

	             --------------------------------------------------

	             To: james.kirck@startrek.com;eliot.ness@untouchables.com
	             BCC:
                     Subject: invitation subject
                     Core Text body as entered by sender himself
	             <Please Click Here> (just a text, no links underneath)

	               --------------------------------------------------



